Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1133

reference: 857-tree-1
name: 1133
tree-preservation-order: undefined
857-tpo-1
uprn
address-text
point: POINT (-0.955461 50.867979)
geometry: MULTIPOLYGON (((-0.955390 50.867971,-0.955393 50.867985,-0.955403 50.867998,-0.955418 50.868008,-0.955438 50.868014,-0.955460 50.868017,-0.955482 50.868015,-0.955502 50.868008,-0.955518 50.867999,-0.955528 50.867986,-0.955532 50.867972,-0.955529 50.867958,-0.955519 50.867946,-0.955504 50.867936,-0.955484 50.867929,-0.955462 50.867927,-0.955440 50.867929,-0.955420 50.867935,-0.955404 50.867945,-0.955394 50.867957,-0.955390 50.867971)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL